Welcome Guest, you are in: Login
CTS Futures

Page History: Logon

Compare Page Revisions



« Older Revision - Back to Page History - Newer Revision »


Page Revision: 2012/09/06 16:13


Session Initiation

After a successful TCP (socket) connection, the T4 FIX API basic requirement is to have both the Initiator and Acceptor start with sequence number 1. The client will initiate the FIX Session by sending a Logon Message to the T4 FIX API server. Successful authentication will be responded with a Logon message echo. The Password field (Tag 96) of the API server logon message will be identified with an asterisk.

Drop of a physical connection will result in the end of a FIX Session. Upon reconnection, the client is required to start a new FIX Session with sequence number 1. The T4 API server will appropriately respond with messages starting with sequence number 1.

Authentication Requirements

After a successful physical connection to the T4 FIX API server, authenticated access is achieved with the following parameters in the client's Logon message:

Tag NameTag NumberDescription
TargetCompId56FIX API System
SenderCompId49Firm Name
SecureData91Application ID (FIX API ID)
SecureDataLen90Length of Application ID string
SenderSubId50Firm User Name (Trader name, desk, etc.)
RawData96Firm User Password
RawDataLen95Length of Firm User Password string

Failure to provide the correct parameters in the Logon message will result in an logon failure. Appropriately, a Logout message will be sent to the client. The Logout message will contain a short description of the failure to help determine the cause of failed authentication. Thereafter, a physical disconnection will occur. As the FIX Session failed, the T4 FIX API will expect a new attempt for a new FIX session. The next Logon message (from the client) must start with sequence number 1.

Message Dictionary

TagField NameReq'dComments
Standard HeaderYMsgType = A
91SecureDataYFIX API ID. Please contact your FIX API Administrator for your authorized id.
90SecureDataLenYLength of SecureData string
49SenderCompIDY Assigned value used to identify firm sending message
56TargetCompIDY Assigned value used to identify receiving firm
50SenderSubIDY Assigned value used to identify specific message originator (trader, desk, etc.)
BodyY
98EncryptMethodY(Always unencrypted). Value = None
108HeartBtIntYHeartbeat interval. Set to 30 seconds.
95RawDataLengthYLength of user Password string
96RawDataYPassword for user authentication
141ResetSeqNumFlagNNot used. Indicates both sides of a FIX session should reset sequence numbers
383MaxMessageSizeNNot used. Can be used to specify the maximum number of bytes supported for messages received
384NoMsgType GroupNNot used. Specifies the number of repeating MsgTypes specified
Standard TrailerY

Sample Message

34=1|49=test|56=T4Test|50=TraderName|52=20120904-17:37:16.848|91=64768859-3DCF-4214-A4E8-DA66881AFC63|90=36|95=10|96=_password_|98=None|108=30|

[FIXLOGIN]
[MsgSeqNum] 34 = 1
[SenderCompID] 49 = test
[TargetCompID] 56 = T4Test
[SenderSubID] 50 = TraderName
[SendingTime] 52 = 20120904-17:33:50.398
[SecureData] 91 = 64768859-3DCF-4214-A4E8-DA66881AFC63
[SecureDataLen] 90 = 36
[RawDataLength] 95 = 10
[RawData] 96 = _password_
[EncryptMethod] 98 = None
[HeartBtInt] 108 = 30

FIX API Home Page.

Trade how you want, where you want

support@ctsfutures.com (312) 939 0164

2 Pierce Pl, Suite 200, Itasca, IL 60143

© 2009-2023 Cunningham Trading Systems LLC All rights reserved.